This stack layer connects role grant and revoke behavior through frontend handlers, privilege checks, membership cache refresh, and the session surfaces needed by role dispatch. It also carries the SET ROLE/session plumbing required to keep the restored dispatch code compile-safe.\n\nConstraint: Frontend GRANTED BY and role dispatch depend on membership snapshots and session user accessors.\nRejected: Keep handler dispatch as parser-only stubs | would prevent testing the meta authority added by the previous PRs.\nConfidence: medium\nScope-risk: moderate\nDirective: Catalog compatibility and system function snapshots still belong to the final stack layer.\nTested: cargo fmt --check; cargo check -p risingwave_frontend\nNot-tested: Full role_dispatch integration test suite

Actual SELECT/UPDATE binding now uses the same role-membership inheritance helper as session privilege checks instead of checking only direct ACLs on the current role. This keeps runtime table access aligned with the effective privilege model introduced in the frontend role-dispatch layer.

Constraint: The fix belongs in PR #25525 because that stack layer owns frontend privilege checks, effective privilege helpers, and membership cache plumbing.

Rejected: Put this in #25527 catalog compatibility | that would leave actual query execution broken until the final catalog-only layer.

Confidence: high

Scope-risk: narrow

Directive: Keep pg_catalog/system-function compatibility in #25527; this commit only wires actual binder checks to effective privileges.

Tested: cargo fmt --check; git diff --check; cargo check -p risingwave_frontend; cargo test -p risingwave_frontend --test role_dispatch; ./risedev slt-clean './e2e_test/ddl/role_inherited_privilege.slt'; ./risedev slt './e2e_test/ddl/role_inherited_privilege.slt'

Not-tested: Full workspace CI

Co-authored-by: OmX <omx@oh-my-codex.dev>